Dynamic Overwriting of Physical Downlink Control Channel for Hybrid Automatic Repeat Request Associations for Downlink Semi-Persistent Scheduling

ABSTRACT

A method for assigning hybrid automatic repeat request (HARQ) process ID is provided. The method includes, when a retransmission associated with a first initial semi-persistent scheduling (SPS) transmission having a first HARQ process ID is expected to occur after a second initial transmission previously configured with SPS resource, explicitly assigning a second HARQ process ID to the second initial transmission wherein the second HARQ process ID is different from the first HARQ process ID.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority to U.S. provisional patent application No. 61/086,074, filed Aug. 4, 2008, by Zhijun Cai, et al, entitled “Dynamic Overwriting of Physical Downlink Control Channel for Hybrid Automatic Repeat Request Associations for Downlink Semi-Persistent Scheduling” (34000-US-PRV—4214-10500), which is incorporated by reference herein as if reproduced in its entirety.

BACKGROUND

As used herein, the terms “user agent” and “UA” can refer to mobile devices such as mobile telephones, personal digital assistants, handheld or laptop computers, and similar devices that have telecommunications capabilities. Such a UA might consist of a wireless device and its associated Universal Integrated Circuit Card (UICC) that includes a Subscriber Identity Module (SIM) application, a Universal Subscriber Identity Module (USIM) application, or a Removable User Identity Module (R-UIM) application or might consist of the device itself without such a card. The term “UA” may also refer to devices that have similar capabilities but that are not transportable, such as desktop computers, set-top boxes, or network nodes. When a UA is a network node, the network node could act on behalf of another function such as a wireless device and simulate or emulate the wireless device or fixed line device. For example, for some wireless devices, the IP (Internet Protocol) Multimedia Subsystem (IMS) Session Initiation Protocol (SIP) client that would typically reside on the device actually resides in the network and relays SIP message information to the device using optimized protocols. In other words, some functions that were traditionally carried out by a wireless device can be distributed in the form of a remote UA, where the remote UA represents the wireless device in the network. The term “UA” can also refer to any hardware or software component that can terminate a SIP session.

In traditional wireless telecommunications systems, transmission equipment in a base station transmits signals throughout a geographical region known as a cell. As technology has evolved, more advanced equipment has been introduced that can provide services that were not possible previously. This advanced equipment might include, for example, an evolved node B (ENB) rather than a base station or other systems and devices that are more highly evolved than the equivalent equipment in a traditional wireless telecommunications system. Such advanced or next generation equipment may be referred to herein as long-term evolution (LTE) equipment, and a packet-based network that uses such equipment can be referred to as an evolved packet system (EPS). As used herein, the term “access device” will refer to any component, such as a traditional base station or an LTE ENB that can provide a UA with access to other components in a telecommunications system. In an EPS system a UA is often referred to as user equipment (UE).

For a wireless Voice over Internet Protocol (VoIP) call, the signal that carries data between a UA and an access device can have a specific set of frequency, time, and coding parameters and other characteristics that might be specified by the access device. A connection between a UA and an access device that has a specific set of such characteristics can be referred to as a resource. An access device typically establishes a different resource for each UA with which it is communicating at any particular time.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of this disclosure, reference is now made to the following brief description, taken in connection with the accompanying drawings and detailed description, wherein like reference numerals represent like parts.

FIG. 1 is an illustration of data transmissions and retransmissions according to an embodiment of the disclosure.

FIG. 2 is an alternative illustration of data transmissions and retransmissions according to an embodiment of the disclosure.

FIG. 3 is a diagram of a method for associating initial transmissions and retransmissions according to an embodiment of the disclosure.

FIG. 4 is a diagram of a wireless communications system including a user agent operable for some of the various embodiments of the disclosure.

FIG. 5 is a block diagram of a user agent operable for some of the various embodiments of the disclosure.

FIG. 6 is a diagram of a software environment that may be implemented on a user agent operable for some of the various embodiments of the disclosure.

FIG. 7 is an illustrative general purpose computer system suitable for some of the various embodiments of the disclosure.

FIGS. 8 a, 8 b, and 8 c are alternative illustrations of data transmissions and retransmissions according to an embodiment of the disclosure.

FIG. 9 depicts UA geometry in a cell.

DETAILED DESCRIPTION

It should be understood at the outset that although illustrative implementations of one or more embodiments of the present disclosure are provided below, the disclosed systems and/or methods may be implemented using any number of techniques, whether currently known or in existence. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary designs and implementations illustrated and described herein, but may be modified within the scope of the appended claims along with their full scope of equivalent.

In an embodiment, a method is provided for assigning hybrid automatic repeat request (HARQ) process ID. The method includes, when a retransmission associated with a first initial semi-persistent scheduling (SPS) transmission having a first HARQ process ID is expected to occur after a second initial transmission previously configured with SPS resource, explicitly assigning a second HARQ process ID to the second initial transmission wherein the second HARQ process ID is different from the first HARQ process ID.

In an alternative embodiment, an access device is provided. The access device includes a transmitter configured such that, when a retransmission associated with a first initial semi-persistent scheduling (SPS) transmission having a first hybrid automatic repeat request (HARQ) process ID is expected to occur after a second initial transmission previously configured with SPS resource, the access device explicitly assigns a second HARQ process ID to the second initial transmission, wherein the second HARQ process ID is different from the first HARQ process ID.

In an alternative embodiment, a user equipment is provided. The user equipment includes a receiver configured such that, when a retransmission associated with a first initial semi-persistent scheduling (SPS) transmission having a first hybrid automatic repeat request (HARQ) process ID is expected to occur after a second initial transmission previously configured with SPS resource, the user equipment receives a second HARQ process ID explicitly assigned to the second initial transmission, wherein the second HARQ process ID is different from the first HARQ process ID.

The procedure of determining a transmission resource one time and then periodically reallocating substantially the same resource can be referred to as semi-persistent scheduling (also referred to as configured scheduling). In semi-persistent scheduling, there is infrequent PDCCH (Physical Downlink Control Channel) notification about recurring resource availability for a UA; hence the signaling overhead in both the uplink and the downlink is reduced. That is, in semi-persistent scheduling, the resource provided to multiple data packets is allocated based on a single scheduling request.

Hybrid Automatic Repeat Request (HARQ) is an error control method sometimes used in digital telecommunications, including data transmissions that use semi-persistent scheduling. In HARQ, additional error detection and correction bits can be added to a data transmission. If the recipient of the transmission is able to successfully decode the data transmission, then the recipient accepts the data block associated with the transmission. If the recipient is not able to decode the transmission, the recipient might request a retransmission.

FIG. 1 illustrates a series of data transmissions from an access device 120 to a UA 110. The data transmissions include initial transmissions 210 and retransmissions 220 that occur when the UA 110 does not successfully receive one or more initial transmissions 210. The initial transmissions 210 include the HARQ error detection bits and occur at periodic packet arrival intervals 230, e.g., 20 milliseconds for voice over internet protocol (VoIP). Upon receiving an initial transmission 210, the UA 110 attempts to decode the error detection bits. If the decoding is successful, the UA 110 accepts the data packet associated with the initial data transmission 210 and sends an acknowledgement (ACK) message to the access device 120. If the decoding is unsuccessful, the UA 110 places the data packet associated with the initial data transmission 210 in a buffer and sends a non-acknowledgement (NACK) message to the access device 120.

If the access device 120 receives a NACK message, the access device 120 sends a retransmission 220 a of the initial transmission 210. The retransmission may contain different data meant to be combined with the initial transmission that is sitting in the buffer. The retransmissions 220 a, like the initial transmissions 210 a, include HARQ error correction and detection bits. If the decoding of a retransmission 220 a together with its corresponding initial transmission 210 a is unsuccessful, the UA 110 might send another NACK message, and the access device might send another retransmission 220 b. The UA 110 typically combines an initial transmission 210 a and its corresponding retransmissions 220 a, 220 b before the decoding. The interval between an initial transmission 210 and its first retransmission 220 a or between two retransmissions 220 a, 220 b is often referred to as the retransmission time 240.

The process of the access device 120 sending the UA 110 an initial transmission 210, the UA 110 attempting to decode the transmission, the access device 120 waiting for an ACK or NACK message from the UA 110, and the access device 120 sending a retransmission 220 when a NACK message is received and the UA 110 attempting to successfully decode the combined transmission and retransmissions can be referred to as a HARQ process. The access device 120 can support only a limited number of HARQ processes, e.g., eight for one embodiment of an EPS system. Each HARQ process is given a unique ID, and a particular HARQ process ID might be reserved for the exclusive use of one series of data transmissions. For example, if HARQ process ID 1 is reserved for a series of semi-persistently scheduled transmissions, no other transmissions can use HARQ process ID 1.

A HARQ process ID might be designated via control channel signaling, e.g., the PDCCH. For semi-persistent (or configured) scheduling only the very first initial transmission of a talk spurt is assigned via the control channel. Subsequent initial transmissions 210 associated with the semi-persistent (or configured) resource are not assigned via the control channel and therefore have no explicitly assigned HARQ process ID. Only the retransmissions 220 which are assigned via control channel signaling, e.g., the PDCCH, are explicitly assigned a HARQ process ID. Hence there is no direct linkage between the initial transmission 210 and a possible retransmission 220. That is, when the UA 110 receives a retransmission 220, the UA 110 may have to assume that the retransmission 220 is for the most recent initial transmission 210 that requires a retransmission; however, the retransmission may actually be associated with a prior initial transmission 210. If the UA 110 has to assume, it may make the wrong assumption.

This can be illustrated in FIG. 1, where it can be assumed that the UA 110 does not successfully receive a first initial transmission 210 a. It is assumed that the initial transmission 210 a is not the very first transmission (i.e., not signaled on the PDDCH) sent using the semi-persistent (or configured) resource, but is instead an initial transmission that does not have an explicitly assigned HARQ process ID. The UA 110 then sends a NACK to the access device 120. Upon receiving the NACK, the access device 120 sends the UA 110 a first retransmission 220 a. The UA 110 does not successfully receive the first retransmission 220 a and sends another NACK. The access device 120 then sends a second retransmission 220 b, which the UA 110 again does not successfully receive. The UA 110 sends a third NACK, and the access device 120 sends a third retransmission 220 c.

Since a HARQ process ID is explicitly signaled over the PDCCH for each of the retransmissions 220 but not to the initial transmission 210 a, it may not be clear that the retransmissions 220 are associated with the initial transmission 210 a. A simple way to resolve this issue is to reserve a HARQ process ID for all of the initial transmissions 210 and retransmissions 220 for the duration of a session between the access device 120 and the UA 110. In this way, the HARQ process ID explicitly signaled over the PDCCH for the retransmission would be the same as implicitly used by the UA 110 for the initial transmission and the UA 110 would know that retransmissions 220 a and 220 b, for example, are associated with the initial transmission 210 a.

However, some ambiguity might still exist with regard to the third retransmission 220 c, since that retransmission takes place after a second initial transmission 210 b. If one HARQ process ID is set aside for semi-persistently scheduled transmissions, both of the initial transmissions 210 a and 210 b and retransmissions 220 a, 220 b, and 220 c would be using the same HARQ process ID, it would not be clear whether the third retransmission 220 c was associated with the first initial transmission 210 a or the second initial transmission 210 b. This issue might be resolved by reserving two HARQ process IDs and implicitly assigning them to alternating initial transmissions 210. If the UA 110 and the access device 120 are both aware that the two HARQ processes have been reserved in this manner, they can resolve which retransmissions 220 are associated with which initial transmissions 210.

In one embodiment, when a semi-persistent (or configured) transmission is allocated, a message is sent to the UA 110 on the radio resource control (RRC). This RRC message contains the period of the semi-persistent (or configured) transmission. Additionally, this message may include the number of HARQ process IDs that have been reserved for semi-persistent transmissions. Alternatively, both the UA 110 and the access device 120 may already know the number of HARQ process IDs that have been reserved for semi-persistent resources. The UA 110 stores the HARQ process ID information for use when receiving semi-persistently scheduled resources. One skilled in the art will appreciate that other protocols could be used to transmit the period of the semi-persistent transmission and the number of HARQ process IDs that have been reserved for the semi-persistent transmission, including signaling on the PDCCH.

Once the UA 110 knows that a semi-persistent resource has been allocated, the UA 110 will listen for a first initial transmission. In one embodiment, the control signaling for the first initial transmission is sent on a physical downlink control channel (PDCCH). The PDCCH contains the resource blocks (RBs) and modulation and coding scheme (MCS) that will be used for the semi-persistent resource that is always in the same subframe. The UA 110 notes the system frame number (SFN) and subframe in which the RBs and MCS were transmitted on the PDCCH. The UA 110 then looks to another channel, the physical downlink shared channel (PDSCH), to obtain the semi-persistent data in the same subframe. The UA 110 uses the period information to determine when to expect the next initial transmission instead of looking to the control channel, e.g., PDCCH, to determine the next transmission. For example, assume that the first initial transmission occurs at SFN=1, subframe=9 and the period is 20 subframes. The second initial transmission will occur at SFN=3 and subframe=9, assuming that there are 10 subframes per SFN. The UA 110 continues to look to the expected SFN, subframe, and RBs to decode the information in each transmission until the UA 110 receives another message telling the UA 110 to change its behavior.

While reserving HARQ resources can reduce ambiguity, it can also introduce inefficiency. When eight HARQ resources are available, reserving one HARQ resource can reduce peak data throughput of non-semi-persistently scheduled data by 12.5%, and reserving two HARQ resources can reduce peak data throughput of non-semi-persistently scheduled data by 25%. A 12.5% reduction in peak data throughput might be an acceptable tradeoff to ensure that the first retransmission 220 a, for example, is associated with the first initial transmission 210 a, since at least one retransmission 220 typically occurs for approximately 10 to 15% of initial transmissions. However, the 25% reduction in data throughput introduced by the reservation of a second HARQ resource may be excessive. The second HARQ resource can decrease ambiguity when a third retransmission 220 c occurs, but a third retransmission 220 c is very unlikely. For example, a third retransmission 220 c typically occurs for only about 2 to 3% of initial transmissions. In some cases, a larger number of retransmissions is required when UAs are at a cell edge. As is shown in FIG. 9, only a small percentage of UAs are at the cell edge. Such a rare event may not warrant such a large reduction in throughput.

Since the packet arrival interval 230 for semi-persistently scheduled services is typically larger than the retransmission time 240, the first retransmission 220 a and the second retransmission 220 b will typically occur between the first initial transmission 210 a and the second initial transmission 210 b, and the third retransmission 220 c will typically occur after the second initial transmission 210 b. For example, semi-persistently scheduled services such as for voice over internet protocol (VoIP), the packet arrival interval 230 is typically 20 milliseconds while the retransmission time 240 is typically 8 milliseconds. If the number of retransmissions 220 for an initial transmission 210 is limited to two, then the ambiguity associated with the third retransmission 220 c is eliminated, and the reservation of only one HARQ process ID may ensure that the retransmissions 220 a and 220 b are associated with the appropriate initial transmission 210 a.

However, there may be circumstances where the number of retransmissions 220 for an initial transmission 210 is not limited to two. For example, near a cell edge, the third retransmission 220 c may be needed. If the number of retransmissions 220 for an initial transmission 210 is not limited to two, it may be desirable to resolve the ambiguity associated with the third retransmission 220 c in a manner that does not involve an ongoing reservation of a second HARQ process ID in order to improve the throughput performance.

The UA 110 and the access device 120 are both aware of the number of NACK messages that the UA 110 has sent, the number of retransmissions 220 the access device 120 has sent, the size of the packet arrival interval 230, and the length of the retransmission time 240. With this information, the UA 110 and the access device 120 can both recognize when a retransmission 220 associated with a first initial transmission 210 a will occur after a second initial transmission 210 b. For example, the UA 110 and the access device 120 would know that retransmission 220 c will occur after initial transmission 210 b.

In an embodiment, a first HARQ process ID is reserved for all initial transmissions 210 until the UA 110 and the access device 120 become aware that a retransmission 220 associated with a first initial transmission 210 a will occur after a second initial transmission 210 b. At that time, the UA 110 and the access device 120 can agree to follow a rule stating that a second HARQ process ID will be implicitly assigned to the second initial transmission 210 b. In this way the UA 110 and the access device 120 can appropriately link retransmissions 220 associated with the first initial transmission 210 a to the first initial transmission 210 a, and can appropriately link retransmissions 220 associated with the second initial transmission 210 b to the second initial transmission 210 b.

If the total number of retransmissions 220 associated with an initial transmission 210 is limited, initial transmissions 210 that occur after the second retransmission 220 c can revert to using the first HARQ process ID. This allows the second HARQ process ID to be used on a temporary basis only when the rare case occurs of a third retransmission 220 c occurring after a second initial transmission 210 b. Data throughput for non-semi-persistently scheduled data can therefore be increased by almost 12.5% compared to the case where a second HARQ process is reserved throughout a session between the UA 110 and the access device 120.

An example of this embodiment is illustrated in FIG. 2. A first HARQ process, referred to here as HARQ ID-X, is reserved for the initial transmissions 210, including an initial transmission 210 d that occurs before initial transmission 210 a. As in FIG. 1, initial transmission 210 a is unsuccessful, and three retransmissions 220 of initial transmission 210 a occur, with the third retransmission 220 c occurring after a second initial transmission 210 b. Since, in this case, the packet arrival interval is 20 milliseconds and the retransmission time is 8 milliseconds, the UA 110 and the access device 120 are both aware that retransmissions 220 a and 220 b will fall in the first packet arrival interval 230 a and that retransmission 220 c will fall in the second packet arrival interval 230 b. In other embodiments, other packet arrival intervals 230 and retransmission times 240 could be used that would cause retransmissions 220 a and 220 b to fall in the first packet arrival interval 230 a and retransmission 220 c to fall in the second packet arrival interval 230 b.

When the UA 110 is unsuccessful with the second retransmission 230 b, the UA 110 sends a NACK message to the access device 120. At that time, the UA 110 and the access device 120 become aware that the third retransmission 220 c will occur after the second initial transmission 210 b and agree that a second HARQ process ID will be reserved for the second initial transmission 210 b and any retransmissions 220 that might occur for the second initial transmission 210 b. The second HARQ process ID is referred to herein as HARQ ID-Y. If a retransmission 220 d associated with the second initial transmission 210 b occurs, the UA 110 and the access device 120 will both know to implicitly assign HARQ ID-Y to the retransmission 220 d with the second initial transmission 210 b. In other words, when the UA 110 receives both retransmission 220 c and retransmission 220 d during packet arrival interval 230 b, the UA 110 will know that retransmission 220 c is associated with the first initial transmission 210 a and that retransmission 220 d is associated with the second initial transmission 210 b.

If the number of retransmissions 220 for an initial transmission 210 is limited, the UA 110 and the access device 120 are aware that no more retransmissions 220 associated with the first initial transmission 210 a will occur. Therefore, HARQ ID-X is no longer needed at this point to associate retransmissions 220 to the first initial transmission 210 a. HARQ ID-X can therefore be used by initial transmission 210 c and any subsequent initial transmissions 210, and HARQ ID-Y can be released for other purposes. In this way, HARQ ID-Y can be used for only a brief period of time and only on rare occasions, thus increasing overall data throughput compared to the case where two HARQ processes are reserved throughout a session.

The identifier for HARQ ID-Y can be assigned in one of several different ways. In one embodiment, HARQ ID-Y is simply HARQ ID-X+1. For example, if HARQ ID-X is 3, HARQ ID-Y would be 4. In another embodiment, HARQ ID-Y is HARQ ID-X+N, where N is an integer that is explicitly or implicitly assigned by the access device 120. For example, if HARQ ID-X is 5 and the access device 120 assigns a value of 2 to N, the UA 110 and the access device 120 would both be aware that HARQ ID-Y is 7.

In another embodiment, the UA 110 and the access device 120 agree that HARQ ID-Y will be the next HARQ process that is available at the time when it becomes apparent that a third retransmission 220 will occur after a second initial transmission 210. That is, the UA 110 and the access device 120 are both aware of which HARQ process IDs are in use by other UAs and which HARQ process IDs are not being used, and can use the next unused HARQ process ID in the sequence of HARQ process IDs. For example, if the UA 110 and the access device 120 are using HARQ process 2 and are aware that HARQ processes 3 and 4 are being used by other UAs but that HARQ process 5 is not being used, the UA 110 and the access device 120 will use HARQ process 5.

In another embodiment, the access device 120 assigns a value to HARQ ID-Y via radio resource control signaling at the time of session setup, but the HARQ ID-Y process is used only if needed. That is, when a session is being set up between the UA 110 and the access device 120, the access device 120 reserves HARQ ID-X and specifies the HARQ ID-Y process that will be used if a third retransmission 220 occurs after a second initial transmission 210. When such a situation occurs, the UA 110 and the access device 120 know that HARQ ID-Y will be reserved at that time and will use HARQ ID-Y to associate the second initial transmission 210 with any of its retransmissions.

The assignment of the HARQ ID-X and HARQ ID-Y relies upon accurate reception of the ACK/NACK. If there the UA 110 sends an ACK, but the access device 120 interprets this as a NACK, or vice versa, the access device 120 and the UA 110 will have a different understanding of the status of the HARQ process IDs. Thus, an HARQ ID mismatch will occur.

In another embodiment, when the access device 120, for example an eNB, is aware that the third retransmission 220 will occur after the second initial transmission 210, the access device 120 may use dynamic overwriting to transmit the second initial transmission 210. Dynamic overwriting refers to when the access device 120 schedules the initial transmission 210 b, for example dynamically overwriting over the physical downlink control channel (PDCCH) to resolve the HARQ process ID ambiguity, for example by explicitly identifying the HARQ process ID to be associated with the second initial transmission 210. While this approach consumes some additional PDCCH signaling overhead, it provides additional flexibility of use of HARQ process IDs.

Dynamic overwriting is a scheme that the access device 120 uses to overwrite the semi-persistent resource allocation which can apply both the downlink and the uplink. Here we use downlink as an example, the UA 110 is assigned the semi-persistent (or configured) resources in the downlink, and the access device 120 uses this resource to deliver the semi-persistent (or configured) packets to the UA 110. In some cases, the access device 120 may have a large semi-persistently allocated packet coming in that is bigger than the allocated resource, e.g., the number of resource blocks needed to send the large packet is more than the number of resource blocks that were semi-persistently allocated. In this case, the access device will use dynamic scheduling to assign a larger resource to deliver the larger packet. The scheduling information is transmitted over a control channel, e.g., PDCCH, and after the UA 110 receives it, the UA 110 will use this new scheduling information instead of the semi-persistent resource to receive the data from the access device 120. Besides the scenarios for the large packets, in the semi-persistent HARQ process ID assignment situation, the second initial transmission that has been configured (e.g., a transmission that would normally use the semi-persistently allocated resource) may instead be dynamically scheduled using dynamic overwriting allowing the HARQ process ID to be explicitly assigned by the access device over the control channel (e.g., the PDCCH) and that by dynamically scheduling the transmission on the PDCCH, the HARQ process ID is explicitly provided in the PDCCH assignment.

FIG. 3 illustrates an embodiment of a method 300 for associating initial transmissions and retransmissions. At block 310, when a retransmission associated with a first initial transmission having a first HARQ process ID is expected to occur after a second initial transmission, the second initial transmission is given a second HARQ process ID different than the first HARQ process ID, wherein the first HARQ process ID is implicitly assigned and the second HARQ process ID is explicitly assigned. At block 320, when the retransmission associated with the first initial transmission having the first HARQ process ID is not expected to occur after the second initial transmission, the second initial transmission is implicitly assigned the first HARQ process ID.

While the above discussion has focused on downlink communications from the access device 120 to the UA 110, it should be understood that this disclosure could also apply to uplink communications from the UA 110 to the access device 120. In the Uplink case, the control channel is termed as PUCCH (Physical Uplink Control Channel) while the similar scheme can be applied.

FIG. 4 illustrates a wireless communications system including an embodiment of the UA 110. The UA 110 is operable for implementing aspects of the disclosure, but the disclosure should not be limited to these implementations. Though illustrated as a mobile phone, the UA 110 may take various forms including a wireless handset, a pager, a personal digital assistant (PDA), a portable computer, a tablet computer, or a laptop computer. Many suitable devices combine some or all of these functions. In some embodiments of the disclosure, the UA 110 is not a general purpose computing device like a portable, laptop or tablet computer, but rather is a special-purpose communications device such as a mobile phone, a wireless handset, a pager, a PDA, or a telecommunications device installed in a vehicle. In another embodiment, the UA 110 may be a portable, laptop or other computing device. The UA 110 may also be a device, include a device, or be included in a device that has similar capabilities but that is not transportable, a desktop computer, a set-top box, or a network node. The UA 110 may support specialized activities such as gaming, inventory control, job control, and/or task management functions, and so on.

The UA 110 includes a display 402. The UA 110 also includes a touch-sensitive surface, a keyboard or other input keys generally referred as 404 for input by a user. The keyboard may be a full or reduced alphanumeric keyboard such as QWERTY, Dvorak, AZERTY, and sequential types, or a traditional numeric keypad with alphabet letters associated with a telephone keypad. The input keys may include a trackwheel, an exit or escape key, a trackball, and other navigational or functional keys, which may be inwardly depressed to provide further input function. The UA 110 may present options for the user to select, controls for the user to actuate, and/or cursors or other indicators for the user to direct.

The UA 110 may further accept data entry from the user, including numbers to dial or various parameter values for configuring the operation of the UA 110. The UA 110 may further execute one or more software or firmware applications in response to user commands. These applications may configure the UA 110 to perform various customized functions in response to user interaction. Additionally, the UA 110 may be programmed and/or configured over-the-air, for example from a wireless base station, a wireless access point, or a peer UA 110.

Among the various applications executable by the UA 110 are a web browser, which enables the display 402 to show a web page. The web page may be obtained via wireless communications with a wireless network access node, a cell tower, a peer UA 110, or any other wireless communication network or system 400. The network 400 is coupled to a wired network 408, such as the Internet. Via the wireless link and the wired network, the UA 110 has access to information on various servers, such as a server 410. The server 410 may provide content that may be shown on the display 402. Alternately, the UA 110 may access the network 400 through a peer UA 110 acting as an intermediary, in a relay type or hop type of connection.

FIG. 5 shows a block diagram of the UA 110. While a variety of known components of UAs 110 are depicted, in an embodiment a subset of the listed components and/or additional components not listed may be included in the UA 110. The UA 110 includes a digital signal processor (DSP) 502 and a memory 504. As shown, the UA 110 may further include an antenna and front end unit 506, a radio frequency (RF) transceiver 508, an analog baseband processing unit 510, a microphone 512, an earpiece speaker 514, a headset port 516, an input/output interface 518, a removable memory card 520, a universal serial bus (USB) port 522, a short range wireless communication sub-system 524, an alert 526, a keypad 528, a liquid crystal display (LCD), which may include a touch sensitive surface 530, an LCD controller 532, a charge-coupled device (CCD) camera 534, a camera controller 536, and a global positioning system (GPS) sensor 538. In an embodiment, the UA 110 may include another kind of display that does not provide a touch sensitive screen. In an embodiment, the DSP 502 may communicate directly with the memory 504 without passing through the input/output interface 518.

The DSP 502 or some other form of controller or central processing unit operates to control the various components of the UA 110 in accordance with embedded software or firmware stored in memory 504 or stored in memory contained within the DSP 502 itself. In addition to the embedded software or firmware, the DSP 502 may execute other applications stored in the memory 504 or made available via information carrier media such as portable data storage media like the removable memory card 520 or via wired or wireless network communications. The application software may comprise a compiled set of machine-readable instructions that configure the DSP 502 to provide the desired functionality, or the application software may be high-level software instructions to be processed by an interpreter or compiler to indirectly configure the DSP 502.

The antenna and front end unit 506 may be provided to convert between wireless signals and electrical signals, enabling the UA 110 to send and receive information from a cellular network or some other available wireless communications network or from a peer UA 110. In an embodiment, the antenna and front end unit 506 may include multiple antennas to support beam forming and/or multiple input multiple output (MIMO) operations. As is known to those skilled in the art, MIMO operations may provide spatial diversity which can be used to overcome difficult channel conditions and/or increase channel throughput. The antenna and front end unit 506 may include antenna tuning and/or impedance matching components, RF power amplifiers, and/or low noise amplifiers.

The RF transceiver 508 provides frequency shifting, converting received RF signals to baseband and converting baseband transmit signals to RF. In some descriptions a radio transceiver or RF transceiver may be understood to include other signal processing functionality such as modulation/demodulation, coding/decoding, interleaving/deinterleaving, spreading/despreading, inverse fast Fourier transforming (IFFT)/fast Fourier transforming (FFT), cyclic prefix appending/removal, and other signal processing functions. For the purposes of clarity, the description here separates the description of this signal processing from the RF and/or radio stage and conceptually allocates that signal processing to the analog baseband processing unit 510 and/or the DSP 502 or other central processing unit. In some embodiments, the RF Transceiver 508, portions of the Antenna and Front End 506, and the analog baseband processing unit 510 may be combined in one or more processing units and/or application specific integrated circuits (ASICs).

The analog baseband processing unit 510 may provide various analog processing of inputs and outputs, for example analog processing of inputs from the microphone 512 and the headset 516 and outputs to the earpiece 514 and the headset 516. To that end, the analog baseband processing unit 510 may have ports for connecting to the built-in microphone 512 and the earpiece speaker 514 that enable the UA 110 to be used as a cell phone. The analog baseband processing unit 510 may further include a port for connecting to a headset or other hands-free microphone and speaker configuration. The analog baseband processing unit 510 may provide digital-to-analog conversion in one signal direction and analog-to-digital conversion in the opposing signal direction. In some embodiments, at least some of the functionality of the analog baseband processing unit 510 may be provided by digital processing components, for example by the DSP 502 or by other central processing units.

The DSP 502 may perform modulation/demodulation, coding/decoding, interleaving/deinterleaving, spreading/despreading, inverse fast Fourier transforming (IFFT)/fast Fourier transforming (FFT), cyclic prefix appending/removal, and other signal processing functions associated with wireless communications. In an embodiment, for example in a code division multiple access (CDMA) technology application, for a transmitter function the DSP 502 may perform modulation, coding, interleaving, and spreading, and for a receiver function the DSP 502 may perform despreading, deinterleaving, decoding, and demodulation. In another embodiment, for example in an orthogonal frequency division multiplex access (OFDMA) technology application, for the transmitter function the DSP 502 may perform modulation, coding, interleaving, inverse fast Fourier transforming, and cyclic prefix appending, and for a receiver function the DSP 502 may perform cyclic prefix removal, fast Fourier transforming, deinterleaving, decoding, and demodulation. In other wireless technology applications, yet other signal processing functions and combinations of signal processing functions may be performed by the DSP 502.

The DSP 502 may communicate with a wireless network via the analog baseband processing unit 510. In some embodiments, the communication may provide Internet connectivity, enabling a user to gain access to content on the Internet and to send and receive e-mail or text messages. The input/output interface 518 interconnects the DSP 502 and various memories and interfaces. The memory 504 and the removable memory card 520 may provide software and data to configure the operation of the DSP 502. Among the interfaces may be the USB interface 522 and the short range wireless communication sub-system 524. The USB interface 522 may be used to charge the UA 110 and may also enable the UA 110 to function as a peripheral device to exchange information with a personal computer or other computer system. The short range wireless communication sub-system 524 may include an infrared port, a Bluetooth interface, an IEEE 802.11 compliant wireless interface, or any other short range wireless communication sub-system, which may enable the UA 110 to communicate wirelessly with other nearby mobile devices and/or wireless base stations.

The input/output interface 518 may further connect the DSP 502 to the alert 526 that, when triggered, causes the UA 110 to provide a notice to the user, for example, by ringing, playing a melody, or vibrating. The alert 526 may serve as a mechanism for alerting the user to any of various events such as an incoming call, a new text message, and an appointment reminder by silently vibrating, or by playing a specific pre-assigned melody for a particular caller.

The keypad 528 couples to the DSP 502 via the interface 518 to provide one mechanism for the user to make selections, enter information, and otherwise provide input to the UA 110. The keyboard 528 may be a full or reduced alphanumeric keyboard such as QWERTY, Dvorak, AZERTY and sequential types, or a traditional numeric keypad with alphabet letters associated with a telephone keypad. The input keys may include a trackwheel, an exit or escape key, a trackball, and other navigational or functional keys, which may be inwardly depressed to provide further input function. Another input mechanism may be the LCD 530, which may include touch screen capability and also display text and/or graphics to the user. The LCD controller 532 couples the DSP 502 to the LCD 530.

The CCD camera 534, if equipped, enables the UA 110 to take digital pictures. The DSP 502 communicates with the CCD camera 534 via the camera controller 536. In another embodiment, a camera operating according to a technology other than Charge Coupled Device cameras may be employed. The GPS sensor 538 is coupled to the DSP 502 to decode global positioning system signals, thereby enabling the UA 110 to determine its position. Various other peripherals may also be included to provide additional functions, e.g., radio and television reception.

FIG. 6 illustrates a software environment 602 that may be implemented by the DSP 502. The DSP 502 executes operating system drivers 604 that provide a platform from which the rest of the software operates. The operating system drivers 604 provide drivers for the UA hardware with standardized interfaces that are accessible to application software. The operating system drivers 604 include application management services (“AMS”) 606 that transfer control between applications running on the UA 110. Also shown in FIG. 6 are a web browser application 608, a media player application 610, and Java applets 612. The web browser application 608 configures the UA 110 to operate as a web browser, allowing a user to enter information into forms and select links to retrieve and view web pages. The media player application 610 configures the UA 110 to retrieve and play audio or audiovisual media. The Java applets 612 configure the UA 110 to provide games, utilities, and other functionality. A component 614 might provide functionality described herein.

The UA 110 and other components described above might include a processing component that is capable of executing instructions related to the actions described above. FIG. 7 illustrates an example of a system 1300 that includes a processing component 1310 suitable for implementing one or more embodiments disclosed herein. In addition to the processor 1310 (which may be referred to as a central processor unit or CPU), the system 1300 might include network connectivity devices 1320, random access memory (RAM) 1330, read only memory (ROM) 1340, secondary storage 1350, and input/output (I/O) devices 1360. In some cases, some of these components may not be present or may be combined in various combinations with one another or with other components not shown. These components might be located in a single physical entity or in more than one physical entity. Any actions described herein as being taken by the processor 1310 might be taken by the processor 1310 alone or by the processor 1310 in conjunction with one or more components shown or not shown in the drawing.

The processor 1310 executes instructions, codes, computer programs, or scripts that it might access from the network connectivity devices 1320, RAM 1330, ROM 1340, or secondary storage 1350 (which might include various disk-based systems such as hard disk, floppy disk, or optical disk). While only one processor 1310 is shown, multiple processors may be present. Thus, while instructions may be discussed as being executed by a processor, the instructions may be executed simultaneously, serially, or otherwise by one or multiple processors. The processor 1310 may be implemented as one or more CPU chips.

The network connectivity devices 1320 may take the form of modems, modem banks, Ethernet devices, universal serial bus (USB) interface devices, serial interfaces, token ring devices, fiber distributed data interface (FDDI) devices, wireless local area network (WLAN) devices, radio transceiver devices such as code division multiple access (CDMA) devices, global system for mobile communications (GSM) radio transceiver devices, worldwide interoperability for microwave access (WiMAX) devices, and/or other well-known devices for connecting to networks. These network connectivity devices 1320 may enable the processor 1310 to communicate with the Internet or one or more telecommunications networks or other networks from which the processor 1310 might receive information or to which the processor 1310 might output information.

The network connectivity devices 1320 might also include one or more transceiver components 1325 capable of transmitting and/or receiving data wirelessly in the form of electromagnetic waves, such as radio frequency signals or microwave frequency signals. Alternatively, the data may propagate in or on the surface of electrical conductors, in coaxial cables, in waveguides, in optical media such as optical fiber, or in other media. The transceiver component 1325 might include separate receiving and transmitting units or a single transceiver. Information transmitted or received by the transceiver 1325 may include data that has been processed by the processor 1310 or instructions that are to be executed by processor 1310. Such information may be received from and outputted to a network in the form, for example, of a computer data baseband signal or signal embodied in a carrier wave. The data may be ordered according to different sequences as may be desirable for either processing or generating the data or transmitting or receiving the data. The baseband signal, the signal embedded in the carrier wave, or other types of signals currently used or hereafter developed may be referred to as the transmission medium and may be generated according to several methods well known to one skilled in the art.

The RAM 1330 might be used to store volatile data and perhaps to store instructions that are executed by the processor 1310. The ROM 1340 is a non-volatile memory device that typically has a smaller memory capacity than the memory capacity of the secondary storage 1350. ROM 1340 might be used to store instructions and perhaps data that are read during execution of the instructions. Access to both RAM 1330 and ROM 1340 is typically faster than to secondary storage 1350. The secondary storage 1350 is typically comprised of one or more disk drives or tape drives and might be used for non-volatile storage of data or as an over-flow data storage device if RAM 1330 is not large enough to hold all working data. Secondary storage 1350 may be used to store programs that are loaded into RAM 1330 when such programs are selected for execution.

The I/O devices 1360 may include liquid crystal displays (LCDs), touch screen displays, keyboards, keypads, switches, dials, mice, track balls, voice recognizers, card readers, paper tape readers, printers, video monitors, or other well-known input devices. Also, the transceiver 1325 might be considered to be a component of the I/O devices 1360 instead of or in addition to being a component of the network connectivity devices 1320. Some or all of the I/S devices 1360 may be substantially similar to various components depicted in the previously described drawing of the UA 110, such as the display 402 and the input 404.

The following is an alternative embodiment of the disclosure.

I. DL SPS HARQ Process

HARQ process ID ambiguity has several issues. The first issue is that when a DL SPS retransmission occurs, the UE needs to associate the possible retransmission (with HARQ Process ID via PDCCH signaling) with the initial transmission that is sitting in one of the HARQ buffers. However, the initial SPS transmission is not assigned on a PDCCH and, hence, has no associated HARQ process ID. This makes the linkage between the initial transmission and the retransmission and soft combining difficult. A PDCCH is used to signal the UE that the retransmission is coming; however, it is not clear what HARQ process ID to use. The second issue, shown in the middle of FIG. 8 a, occurs when a retransmission occurs after the next SPS transmission. The UE has no way of associating the retransmission with the correct transmission.

A simple way to resolve these issues is to reserve the HARQ Processes for the DL SPS. In the following, we will further analyze the details.

II. HARQ Process Reservation

The need to link the transmission with the retransmission is important since retransmissions will happen on 10-15% of transmitted voice packets. A simple and robust way to resolve this is to reserve one of the HARQ processes in order to link the initial transmission and the HARQ retransmissions. A simple example of this would be to reserve HARQ process 1 for SPS. No dynamically scheduled transmissions would be allowed to use HARQ process 1 when it is in use. When SPS is configured, the UE would automatically use process 1 for all transmission and re-transmissions.

If two HARQ processes are reserved and mapped to the SFN and/or subframe, then the second issue is also resolved. An example of this would be that HARQ process 1 and HARQ process 2 are used cyclically every 20 ms interval (so the HARQ usage pattern is 1, 2, 1, 2, 1, 2 . . . ). However, this can be inefficient, especially considering that retransmissions continuing for more than a frame do not occur very often (on the order of 1% by system design). Given that the initial transmission is targeted for 10-15% BLER and a 20 ms packet arrival interval can accommodate 2 HARQ FDD retransmissions, the probability that the second case may occur is quite low (note that VoIP BLER is targeted for less than 1%). It may not be efficient to reserve another HARQ process to resolve the unlikely occurring second issue. Obviously, the HARQ process reservation will reduce the throughput of the UE since non-continuous transmissions may occur when less than 8 HARQ processes are used due to the reservation.

Further, FIG. 9 shows the geometry of the UEs uniformly distributed in a cell. We can see that only a small percentage of the UEs are at the cell edge which may require more retransmissions. However, for the UEs in the medium/good radio conditions, in general, the needed number of retransmissions is very limited. For these UEs, single HARQ process is almost enough in most cases. If we always reserve two HARQ process, it will be a waste for these UEs. Hence, it may be necessary to design a flexible way to assign the HARQ process for the SPS.

As an example, if we assume the maximum number of HARQ retransmissions for the SPS is limited by 2 for FDD, we do not even need to worry about the second issue at all and only one HARQ process is required for the SPS as is shown in FIG. 8 b. Therefore, given that one HARQ process is reserved for a VoIP session, it is beneficial to explore how to avoid the reservation of another HARQ process just for infrequent second case.

Considering that both the UE and the eNB have exactly the same information from the SPS allocations, the UE can know that the ambiguity will occur when it transmits the NACK. It need only know the NACK-to-retransmission RTT and when it is sent. After the eNB receives the NACK, eNB can also be aware that ambiguity will occur when the eNB sends the retransmission. Therefore, it is possible to find a way to dynamically allocate the HARQ process ID that allows the UE to resolve the second case. There are two possible ways.

1. Implicit Rule.

Here is an example. Assume that the reserved HARQ process is X, and the dynamically allocated HARQ process is X+1 (but not reserved). Whenever the UE sends a NACK but the expected retransmission will cross the 20 ms boundary, the UE will assume the coming initial transmission over the SPS is using HARQ process X+1. After the eNB receives the NACK and becomes aware that the retransmission will cross the 20 ms boundary, the eNB will use the HARQ process ID X+1 (increment the ID Mod 8) to identity it as the initial transmission (also the corresponding retransmission for this transmission). Therefore, in the next 20 ms interval, if the UE receives a retransmission with HARQ process X, it is aware that this is for the first transmission; if the UE receives a retransmission with HARQ process X+1, it is aware that this is linked to the current (second) initial transmission. Please see FIG. 8 c.

Note that in FIG. 8 c, the HARQ process ID for transmission 7 will be revert to the reserved HARQ process ID=X for the normal use (only HARQ process X is reserved). Note that in this case even though transmission 6 needs more than 2 retransmissions (HARQ retransmissions for transmission 6 will cross the transmission 7 boundary), there is no ambiguity for the correct HARQ combing.

The above scheme is just an example that we use the additional HARQ process as X+1. There are several ways:

-   -   1) The additional HARQ process can be the next available HARQ         process in the time that case 2 occurs. Note that eNB and the UE         has the same information on the HARQ usage status.     -   2) The additional HARQ process is assigned by the eNB through         RRC signalling. But only in case that case 2 occurs. Otherwise         it is not used by SPS (no reservation).

The above method relies on an accurate reception of the ACK/NACK. If the ACK→NACK or NACK→ACK errors occur, the eNB and the UE may have different understanding. However, we believe this case occurs rarely. As we described above, the second case happens infrequently; and then given the second case happens, the NACK/ACK error probability then equals to Prob(NACK/ACK error)*Prob(second case occur). Note that NACK/ACK error is in 10̂(−3) to 10{circumflex over (0)}(−4) range [3] and second case occurs normally less than 5%. So the total probability is in the range of 10{circumflex over (0)}(−5) to 10{circumflex over (0)}(−6).

If these errors do happen (uses FIG. 8 c as an example),

-   -   a) For a NACK→ACK error, the eNB will stop the retransmission         for transmission 5, and still implicitly allocate the HARQ         process X to transmission 6. The UE will assume transmission 6         uses HARQ process X+1. If transmission 6 is successful, there is         no problem. If the transmission 6 is in error, when the         retransmission comes (so always HARQ process X), the UE will         combine it with transmission 5. The worst case is that UE may         lose one more voice packet. The error will not be propagated         (since in transmission 7, both the eNB and the UE will simply         apply HARQ process X).     -   b) For an ACK→NACK error, transmission 5 is successful and UD         assumes transmission 6 uses the HARQ ID=X. If the transmission 6         is successful, there is no problem. If transmission 6 is in         error, the eNB will send the retransmission with HARQ process         ID=x+1. The UE will not try to perform the HARQ combining due to         the HARQ ID mismatch. The worst case is that the UE may lose one         more packet for transmission 6. The error will not be propagated         (since in transmission 7, both the eNB and the UE will simply         apply HARQ process X).

From the above analysis, we conclude that only one HARQ process reservation for the VoIP is necessary, and another HARQ process is implicitly and dynamically assigned to handle the infrequent second case. In this way, only one HARQ is needed to be reserved (compared with 2 HARQ process reservations, this increase the throughput by 17% for the UE).

2. Dynamic Overwriting

When the eNB is aware that the ambiguity occurs, i.e., the coming scheduled retransmission for the initial transmission N will happen after the next initial transmission N+1, the eNB will use dynamic overwriting to transmit the initial transmission N+1. In FIG. 5 c, for the transmission 6, the eNB will use dynamic overwriting over PDCCH to resolve the ambiguity. Since transmission 6 uses dynamic scheduled transmission, the ambiguity will be resolved. On one hand, this provides additional flexibility to use the HARQ process when infrequent second case occurs. On the other hand, this adds some additional PDCCH signaling overhead.

Proposal 1: One HARQ process is reserved for the SPS. The ENB and UE apply the above described implicit rule or dynamic overwriting to use the additional HARQ process to handle the second case for the SPS.

III. Signaling Aspects

The signaling of the reserved HARQ process ID can be done via the PDCCH or via the RRC.

-   -   1) Via PDCCH     -   Whenever the DL PDCCH SPS activation is received by the UE, the         assigned HARQ ID is the reserved ID X. during the silence         period, no HARQ process ID is reserved.     -   2) Via RRC     -   The eNB will signal the reserved HARQ process ID=X to the UE via         RRC signaling. The reserved HARQ process can be used by other         applications during the silence period. A minor drawback is that         certain flexibility may be lost due to the fixed reservation         (but it seems the impact is negligible). However, this may also         constrain the code space usage for the DL SPS activation via         PDCCH (hence reduce the false detection for DL SPS activation).

From the simplicity and robustness point of view, the signaling of the reserved HARQ process via the RRC signaling seems preferable.

Proposal 2: Using RRC signaling to indicate the reserved HARQ process ID. The reserved HARQ process can be used by other applications during the silence period.

The following 3rd Generation Partnership Project (3GPP) Technical Specifications (TS) are incorporated herein by reference: TS 36.321, TS 36.331, and TS 36.300.

While several embodiments have been provided in the present disclosure, it should be understood that the disclosed systems and methods may be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given herein. For example, the various elements or components may be combined or integrated in another system or certain features may be omitted, or not implemented.

Also, techniques, systems, subsystems and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as coupled or directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component, whether electrically, mechanically, or otherwise. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and could be made without departing from the spirit and scope disclosed herein. 

1. A method for assigning hybrid automatic repeat request (HARQ) process ID, comprising: when a retransmission associated with a first initial semi-persistent scheduling (SPS) transmission having a first HARQ process ID is expected to occur after a second initial transmission previously configured with SPS resource, explicitly assigning a second HARQ process ID to the second initial transmission wherein the second HARQ process ID is different from the first HARQ process ID.
 2. The method of claim 1, wherein the explicit assignment includes information sent via a physical downlink control channel (PDCCH).
 3. The method of claim 1, further comprising: when the retransmission of the first initial SPS transmission having the first HARQ process ID is not expected to occur after the second initial transmission, the second initial transmission is assigned the first HARQ process ID.
 4. The method of claim 1, wherein the first HARQ process ID is reserved via a signaling message, the signaling message being one of a Radio Resource Control (RRC) signaling message or a physical downlink control channel (PDCCH) signaling message.
 5. An access device comprising: a transmitter configured such that, when a retransmission associated with a first initial semi-persistent scheduling (SPS) transmission having a first hybrid automatic repeat request (HARQ) process ID is expected to occur after a second initial transmission previously configured with SPS resource, the access device explicitly assigns a second HARQ process ID to the second initial transmission, wherein the second HARQ process ID is different from the first HARQ process ID.
 6. The access device of claim 5, wherein the explicit assignment includes information sent via a physical downlink control channel (PDCCH).
 7. The access device of claim 5, wherein, when the retransmission of the first initial SPS transmission having the first HARQ process ID is not expected to occur after the second initial transmission, the access device assigns the second initial transmission the first HARQ process ID.
 8. The access device of claim 5, wherein the first HARQ process ID is reserved via a signaling message, the signaling message being one of a Radio Resource Control (RRC) signaling message or a physical downlink control channel (PDCCH) signaling message.
 9. The access device of claim 5, wherein a dynamic transmission of the second transmission occurs by the access device transmitting a control channel message allocating the resources for the second transmission.
 10. A user equipment comprising: a receiver configured such that, when a retransmission associated with a first initial semi-persistent scheduling (SPS) transmission having a first hybrid automatic repeat request (HARQ) process ID is expected to occur after a second initial transmission previously configured with SPS resource, the user equipment receives a second HARQ process ID explicitly assigned to the second initial transmission, wherein the second HARQ process ID is different from the first HARQ process ID.
 11. The user equipment of claim 10, wherein the explicit assignment received by the user equipment includes information sent via a physical downlink control channel (PDCCH).
 12. The user equipment of claim 10, wherein, when the retransmission of the first initial SPS transmission having the first HARQ process ID is not expected to occur after the second initial transmission, the second initial transmission is assigned the first HARQ process ID.
 13. The user equipment of claim 10, wherein the first HARQ process ID is reserved via a signaling message, the signaling message being one of a Radio Resource Control (RRC) signaling message or a physical downlink control channel (PDCCH) signaling message. 